home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
verif33.zip
/
VERIFIER.HST
< prev
next >
Wrap
Text File
|
1992-06-14
|
19KB
|
481 lines
Revision History of the VERIFIER Door
(Most recent changes at the top)
06/13/92 Version 3.3
#1: Changed & improved the initialization routines. My system
increased dramatically from 12-15 seconds down to 2-3 seconds to
initialize (500 records, running 2 nodes under DV on a 386/25)
#2: Added a check for a Maximum security level to answer a script
questionnaire. This is good for controlling script access according
to previous upgrades.
#3: Added Multi-lingual support to several areas: Use the PCBoard
language extension to have multilingual support for these files:
Text display lines have been moved to a separate file - VERITEXT.???
Display files: Use the language extension for other languages
Questionnaires: Use the language extension instead of .DAT
Address Definitions File: Use the language extension instead of .DAT
All of these areas support multi-lingual support. I can't think of
any other area that might need it, but if you do, let me know!
#4: Added security specific file support for all of the display files
listed in the .CFG file(s). In respect to security specific and
language specific file search order: Security specific is searched
first, then language specific. If a security specific file is found,
then it is used, even if a non-security specific language file exists.
#5: Added more character checking in the script answering section.
All keypresses with non-text ASCII entries are ignored (Control
characters except <CR> and backspace, Drawing characters, etc)
Foreign accents and such are accepted.
#6: Added support for the skipping of a display file: If the file is
a zero-length file, the display and the "Press <Any Key> to Continue"
prompt is skipped.
#7: Added support for the new VERIFIER.KEY file.
04/20/92 Version 3.2
#1: Added documentation for the support of non-standard COM ports.
has been available since I recompiled with DoorSource 4.0, but I never
thought about it, since I didn't need it. See VERIFIER.DOC for
details on command line options for non-standard com port usage.
#2: It seems I did some other minor cosmetic changes in the program,
but I didn't keep track of them. What ever I did, it doesn't need any
modifications, and it was to improve appearance or performance...
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 1
Verifier Door Revision History Lance Williams, Author
04/10/92 Version 3.1
#1: Added Security Specific Goodbye screens (First 4 characters
match the file in the .CFG file). (Does anyone want any other screens
to be security specific?? It's easy enough to add.)
#2: Added code to use the new indexes for faster searches.
#3: Recompiled with DoorSource 4.0B
03/03/92 Version 3.01
#1: Added the option to credit users for time in the door. This is
configurable by an entry the configuration file.
#2: Recompiled with a new version of DoorSource that is supposedly
faster on screen writes. Hope it improves things in that area, as the
screen writes are still a little slow for most tastes :-(
#3: Fixed the 25TO30.EXE conversion program and included a
30TO301.EXE conversion program to properly upgrade from both version
2.5 and version 3.0.
02/21/92 Version 3.0
#1: Unlimited Scripts are now available. These are available thru
the new SCRIPTS.DAT file, which controls the access to the various
scripts. See the complete documentation for complete details.
#2: All security upgrade information is moved from the .CFG file over
to the SCRIPTS.DAT file.
#3: Answers to the script questionnaires are now checked for type of
character input. There are 5 different checks that you can choose
from: Alphanumeric (Any Key), Phone Number (0-9,(,),-,[,]) , Numeric
(0-9/,/.), Letters & Punctuation (A-Z & Punct. Keys), Date types (0-9,
/,-) and straight Y/N single character entry. This requires a change
in your script data files, which is handled in the 25TO30.EXE program
(CVTSCR30.EXE for beta testers who have the pre 02/10/92 Ver. 3.0
code)
#4: Due to some inherent bugs in the DOORPCH 3.6 Library for Quick
Basic 4.5, I have recompiled the door in DoorSource 4.0a. Anyone who
was getting DOORPCH errors before, they should be cleared up with this
door routine library. I did have to write all my own error control,
however, so if you find something erroring out, please let me know so
I can correct it. The program will exit to DOS gracefully if an
unrecoverable error does occur.
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 2
Verifier Door Revision History Lance Williams, Author
#5: The script questionnaires now support a MAXIMUM answer length as
well as the minimum it's always had. The overall maximum is set in
the program as 60 characters, so anything over that amount will be set
to 60. This change in your script data files is also handled by
25TO30.EXE or CVTSCR30.EXE.
#6: The door display screens with PCBoard @X## color codes. You can
now cut disk space usage by having only one copy of the screens using
@X## color codes.
#7: Added a CONFIG program to help you set up your initial door
settings. This program will create your VERIFIER.CFG, SCRIPTS.DAT and
individual script data files.
10/02/91 Version 2.5
#1: Found out that the DOORPCH 3.6 Code didn't properly handle 3 word
names. Switched the way the User Name is retrieved. Now gets the
door gets it directly from the USERS file.
#2: The Notices of Conference registrations for the Sysop and Special
scripts were not being displayed. No Message about extra security
was posted either. Fixed.
#3: Just for ease of calculation, the User's Registration number is
now stored in the MAILLIST.DAT file. This is now READ from the
MAILING.EXE program when writing the registration labels. It is also
READ when verifying. The number is only calculated once.
05/09/91 Version 2.4
#1: Added support for making your own prompts to the label questions.
These are now editable from the ADDRESS.EXE program included in this
archive. The system will set them to the default values if you do not
define them, and leave an error message in the caller's log &
VERIFIER.ERR log file. You can setup a maximum of 10 different
formats for your users using the ADDRESS.EXE program included in this
archive. The door also supports a 'generic' format, just asking for a
3rd line if the country they are calling from is not defined. This
will be the last choice in the list your user is given.
#2: Removed Main Menu Option #3, Register as a Visiting Sysop. I
figured with more than one extra script now, that I'd either have to
delete the Sysop Script from the Main Menu or add others, so for now,
I deleted it. If you disagree with my decision, let me know... I may
work something back into the code with version 3.0, which I hope to
have unlimited scripts incorporated into it.......
#3: Full Support for Multiple printers in the Log File, it gets the
printer port from the PCBOARD.DAT file now, not just sending the
output to PRN.
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 3
Verifier Door Revision History Lance Williams, Author
#4: The Userfile name and New User Security are both retrieved from
the PCBOARD.DAT as well, this makes changes to your system setups
transparent to the door program, and automatic... No more adjusting
your .CFG file if you change either of these entries.
#5: The code now also checks, via a new field in the MAILLIST.DAT
file, to see if the user has already verified the registration and it
also checks the database to see if a registration card has yet been
sent to the user. No more verification without a card being sent.
02/08/91 Version 2.3
#1: Added an OPTIONAL 3rd questionnaire, but you will have to add
three lines to your CFG file even if you are not using the optional
script in the door.
VERIFIER.CFG file:
Line #13: Name of the optional script
Line #14: Security & Expiration levels just like SYSOPS Script
Line #15: Added Conferences just like SYSOPS Script
Line #13 must be in a question form, as it is displayed to users if
they want to answer the questionnaire. IE:
Line #13: Are you a MetroLink Hub/Node?
Line #14: 10,0,42
Line #15: 5
If you are not using the optional questionnaire use the folowing in
the CFG file:
Line #13: NULL
Line #14: 0,0,0
Line #15: 0
This will disable the asking of an optional Script questionnaire.
#2: Fixed Display if no Conferences are added for Sysops to display
a message rather than say conference 0 was added.
#3: Added Display of added conferences for the "SPECIAL"
questionnaire added in #1 above.
#4: Added ability to set the expired security level for both Sysops
and regular users. This is a change in your CONFIGURATION FILE:
2 Entries need fixing:
Line #10: Reg. User Temp. Sec., Temp. Expire Days, Expired Security
Line #11: Sysop Temp. Security, Temp. Expire Days, Expired Security
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 4
Verifier Door Revision History Lance Williams, Author
EXAMPLE:
8,35,3 <- Sets Reg. Sec. to 8, Exp. Date to DATE + 35 days, Exp. Sec to 3
9,35,3 <- Sets Sysop Sec. to 9, Exp. Date to DATE + 35 days, Exp. Sec. to 3
#5: Also added the VERIFIER.LOG file to show all door activity in
a file you can review and delete, other than the caller's log.
10/01/90 Version 2.2
#1: Improved Coding for changing expiration date. Now converts to
Julian Date, then adds the amount to change, and converts back to
Gregorian date. Decreased code size by approx. 2K.
#2: Added output to PCBoard CALLERS Log as defined in PCBoard.DAT
file with error control & correction for printer output of caller's
log. Now the code rewrites the PCBOARD.SYS file, turning off the
printer, and dumps the user back to PCBoard with a message to reload
the door, because the error has been corrected, but it was a fatal
error for the program. This option was needed because of bugs in the
DOORPCH library code which was crapping out with my old error code.
#3: Added VERIFIER.ERR file writing for logging bad verification
attempts (IE: Bad Numbers or Re-attempts).
#4: Fixed Bug for New Users who have a MAILLIST.DAT entry (Due to
being deleted from the system, but not from the MAILLIST.DAT file).
Now it updates above user to have a Registration label printed for
him.
#5: Added output to place comment into SYSOP COMMENT #2 that user was
registered/verified via VERIFIER [Version Number]
#6: Fixed small bug that created improper registration numbers in
door if there were trailing spaces after the Sysop's first & last
names, or the BBS Name. Now strips trailing spaces from names.
#7: Removed the ability to enter blank spaces for mailing label
entry. Also improved warning message to make sure the user leaves
proper information.
#8: Rearranged the new user configurations so the user fills out
mailing information before the scripts are answered. No more hanging
up
without filling out mailing label info, and getting upgraded anyway.
#9: Removed the second entry of the registration number & checking
for the same entry.... Couldn't output "*" for numbers entered, so
dropped the idea. (Bugs in DOORPCH.LIB).
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 5
Verifier Door Revision History Lance Williams, Author
08/04/90 Version 2.1
#1: Can now set the Users Expired Security Level when they are
verified. The level is set equal to their interim level after
registration. This way, even after expiration, they will be able to
get into the door to be verified.
#2: Fixed the bug in the expiration date setting, also changed it
to allow for "No Expiration Date" (00-00-00) but setting days till
expiration at 0.
#3: Coded and debugged for Multi-tasking/Multi-node operations.
Thanks to the help of David Douglas, this version is well debugged and
seems fully operational on both Single & Multi-Node Operations.
#4 Small Change in the format of the questionnaire files due to
multi-tasking support... Two lines added to the top of the file:
Line 1: Path/Filename of the ANSWER FILE. (Sysop Definable answer
files now supported!)
Line 2: Number of QUESTIONS found in the questionnaire file. Need
to have only the number of questions, but too large a number
is OK.
#5 The code now checks the answers the length of the answer as it
is being typed. This is partially in preparation for checking content
of the answer which will be in the next version (give me a month or
so!) The code will not accept a <CR> until the Minimum length is
reached, and rings the bell 4 times, and continues onto the next
question, accepting the whole line as the answer. This requires NO
CHANGES in your configurations.
07/13/90 Version 2.0
Added ability to display ANSI/ASCII screens from scripts. Also
removed 2 of the old hard-coded screens from the door and replaced
them with sysop definable screens (Hard-coded names). Also added a
Sysop definable opening & closing screen. I think this makes the door
more pleasing, since you can make it "your own" in a sense. Decided
to call the new release version 2.0 due to the many major changes
in the program.
07/06/90 Version 1.50 (Not Released)
Fixed a small bug in the conference registrations for sysops.
Seems I got variable names mixed up and the User Scans bit map was
getting corrupted. Works fine now.
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 6
Verifier Door Revision History Lance Williams, Author
07/04/90 Version 1.40 (Not Released)
Well, it's a nice holiday, I think I'll work on the program...
Made additional changes to allow display of comments in the scripts.
Also coded in ability to add additional conferences to the user record
of visiting sysops. (Bit mapping is FUN!)
06/21/90 Version 1.30 (Not Released)
Did further changes to add 2 scripts for new users, one for
regular users & one for visiting sysops. What else does anyone really
need?? I may make the door more versatile later on.
06/12/90 Version 1.20 (Not Released)
Got some good ideas from several sysops concerning changes
in the door. Started work coding a script questionnaire section for
make the door a fully functional registration door. My original
intent was to use it as a "back-end" to an existing door, but why
should I register someone else's door when I can write my own!
06/02/90 Version 1.10 (Not Released)
Found a small bug in the mailing list entry module that was not
sorting the MAILLIST.DAT file. Corrected this bug, and things run
marginally faster.
05/19/90 Version 1.00
First general release. After 2 weeks of local testing & no
major problems, I guess it's ready to go. Complete with Mailing List
Manager program for sysop maintenance. I fixed some minor display
typos, but nothing serious.
05/12/90 Version 0.95
Fixed bug where new users were not being flagged properly for
printing of registration label. This was my first run with real users
and printing labels for registration postcards.
05/06/90 Version 0.90
Added Opening and Closing screens. Tested on remote and local
mode. Placed system online on my system for extensive testing by my
users. Started writing this documentation to release the program
officially by May 20th (Hopefully).
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 7
Verifier Door Revision History Lance Williams, Author
05/05/90 Version 0.80
Found that the DOORPCH routines were not working properly on
remote. Screen alignment incorrect on remote systems when using some
of the routines in DP36QB45.LIB. Re-aligned/redesigned the
editor/creator for the mailing list manager part of the door to
accommodate the faulty library.
05/04/90 Version 0.70
Added Ability to have users input their address into the
database from the door. Worked up an editor/creator routine from the
subroutines in MAILING.EXE.
04/30/90 Version 0.60
After a short hiatus from this program, I got back to this one
again. I added better screen displays, and installed some of the
routines from the Sysop Utility for verification checking.
03/05/90 Version 0.50
Initial finished coding for verifier of users. Tested, but
never put online.
__________________________________________________________________
Kadet PCBoard, (315) 245-3815 USR Dual Std. Page 8